Optimize conflict-heavy EVM transfer execution#3405
Conversation
|
The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3405 +/- ##
=======================================
Coverage 59.29% 59.29%
=======================================
Files 2125 2125
Lines 175629 175672 +43
=======================================
+ Hits 104144 104170 +26
- Misses 62404 62416 +12
- Partials 9081 9086 +5
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
7623f7b to
0203fa4
Compare
0203fa4 to
ef8c47c
Compare
PR SummaryMedium Risk Overview Adds a heuristic to detect large blocks (>=64) of simple value-only EVM transfers to a single recipient and forces sequential execution (including bypassing Giga OCC) to avoid OCC retry churn. Optimizes EVM↔Sei association by reusing an existing empty “cast” Reviewed by Cursor Bugbot for commit ef8c47c. Bugbot is set up for automated code reviews on this repo. Configure here. |
Summary
This is split out from #3376 so the behavior changes can be reviewed separately from logging and stress tooling.
Test Plan
go test ./app ./utils/helpers ./app/ante ./x/evm/ante ./x/evm/typesNote
Medium Risk
Changes EVM DeliverTx signature/association flow, account mapping/migration behavior, and block execution routing between OCC and sequential paths; mistakes here could affect transaction validity, nonce/account state, or block processing performance.
Overview
Improves EVM tx processing in conflict-heavy scenarios by reusing already-computed
msg.Derivedsender data during DeliverTx, avoiding repeated signature recovery and adding explicit invalid-pubkey rejection.Adjusts address association to reuse an existing empty “cast” auth account (preserving account number/sequence) when safe, and skips balance migration when the cast address and Sei address are identical.
Adds a heuristic to detect large blocks (>=64) of simple EVM value transfers to a single recipient and forces sequential execution for those blocks (including disabling Giga OCC in that case) to avoid OCC retry churn.
Reviewed by Cursor Bugbot for commit 0203fa4. Bugbot is set up for automated code reviews on this repo. Configure here.